docs(skills): a0-archon-bridge — align with live v2.11 surface + fix :8091 (supersedes #2865) - #2942

…n 404

P2 review finding on #2942: the validation command printed only the
top-level status, which reads "ok" in exactly the failure mode the skill
warns about (connector 404 swallowed into a 200). The one-liner now
checks runtime.status and rejects a 404 note, exiting nonzero on an
unreachable connector.

💘 Generated with Crush

…ills PRs, on-node passes

Adapts pmoves-pair-review and PAIR_REVIEW_RECIPROCITY.md from
parallel-CLAUDE-only to the fleet as it actually is (operator-directed,
during the #2943 review session):

- Any harness counts as the peer surface: Claude Code, Crush, Codex CLI,
  Hermes, KiloCode claws, DeepSeek — cross-harness reviews are the point,
  they surface harness-assumption drift (env vars one launcher sources
  and another doesn't; the TS_Z890 roster drop was this class)
- Fourth reviewer surface: the operator (DARKXSIDE/POWERFULMOVES) as
  Control — both #2942's :8091 correction and #2938's topology challenge
  came from operator pushback on confident agent drafts; gate, don't
  bottleneck
- Harness notes for Crush: same gh/AGNOTE/sign-trail mechanics,
  COMMENTED-not-APPROVED (same-account constraint), sign with the
  agent_signatures.yaml identity, skills-load-on-demand as a trigger-
  quality check
- Skills-PR review checklist mapped to the 4-class taxonomy: frontmatter
  name==dir (Crush validator), description-is-a-trigger, anchors ratchet,
  live-surface probes for port/endpoint claims, Tier 1/Tier 2 CI
- On-node/private review passes: Ollama local models (private by
  construction — motivated by the 2026-09-04 tailnet-address leak),
  hf-agent model nomination, Archon 0.6.0 conversation endpoints for
  tool-using passes, and the already-provisioned coding plans via their
  CLIs — with the leads-not-verdicts guardrail

No behavior change — workflow docs + skill only.

…ills PRs, on-node passes

Adapts pmoves-pair-review and PAIR_REVIEW_RECIPROCITY.md from
parallel-CLAUDE-only to the fleet as it actually is (operator-directed,
during the #2943 review session):

- Any harness counts as the peer surface: Claude Code, Crush, Codex CLI,
  Hermes, KiloCode claws, DeepSeek — cross-harness reviews are the point,
  they surface harness-assumption drift (env vars one launcher sources
  and another doesn't; the TS_Z890 roster drop was this class)
- Fourth reviewer surface: the operator (DARKXSIDE/POWERFULMOVES) as
  Control — both #2942's :8091 correction and #2938's topology challenge
  came from operator pushback on confident agent drafts; gate, don't
  bottleneck
- Harness notes for Crush: same gh/AGNOTE/sign-trail mechanics,
  COMMENTED-not-APPROVED (same-account constraint), sign with the
  agent_signatures.yaml identity, skills-load-on-demand as a trigger-
  quality check
- Skills-PR review checklist mapped to the 4-class taxonomy: frontmatter
  name==dir (Crush validator), description-is-a-trigger, anchors ratchet,
  live-surface probes for port/endpoint claims, Tier 1/Tier 2 CI
- On-node/private review passes: Ollama local models (private by
  construction — motivated by the 2026-09-04 tailnet-address leak),
  hf-agent model nomination, Archon 0.6.0 conversation endpoints for
  tool-using passes, and the already-provisioned coding plans via their
  CLIs — with the leads-not-verdicts guardrail

No behavior change — workflow docs + skill only.

…ills PRs, on-node passes (#2946)

* docs(skills): pair-review goes harness-agnostic — Crush, operator, skills PRs, on-node passes

Adapts pmoves-pair-review and PAIR_REVIEW_RECIPROCITY.md from
parallel-CLAUDE-only to the fleet as it actually is (operator-directed,
during the #2943 review session):

- Any harness counts as the peer surface: Claude Code, Crush, Codex CLI,
  Hermes, KiloCode claws, DeepSeek — cross-harness reviews are the point,
  they surface harness-assumption drift (env vars one launcher sources
  and another doesn't; the TS_Z890 roster drop was this class)
- Fourth reviewer surface: the operator (DARKXSIDE/POWERFULMOVES) as
  Control — both #2942's :8091 correction and #2938's topology challenge
  came from operator pushback on confident agent drafts; gate, don't
  bottleneck
- Harness notes for Crush: same gh/AGNOTE/sign-trail mechanics,
  COMMENTED-not-APPROVED (same-account constraint), sign with the
  agent_signatures.yaml identity, skills-load-on-demand as a trigger-
  quality check
- Skills-PR review checklist mapped to the 4-class taxonomy: frontmatter
  name==dir (Crush validator), description-is-a-trigger, anchors ratchet,
  live-surface probes for port/endpoint claims, Tier 1/Tier 2 CI
- On-node/private review passes: Ollama local models (private by
  construction — motivated by the 2026-09-04 tailnet-address leak),
  hf-agent model nomination, Archon 0.6.0 conversation endpoints for
  tool-using passes, and the already-provisioned coding plans via their
  CLIs — with the leads-not-verdicts guardrail

No behavior change — workflow docs + skill only.

* fix(pair-review): five review-finding corrections to skill + reciprocity doc

- SKILL.md: drop the stale CLAUDE-only "do NOT invoke" block that
  contradicted the harness-agnostic one; operator signs as darkxside/
  powerfulmoves (dsh is not a registered signature identity)
- RECIPROCITY.md: hf-agent is an autonomous HF patrol with no per-diff
  endpoint — reframe as a discovery feed, selection stays with the
  session; Archon is not on every node — probe /api/health (JSON body)
  before offering it; coding-plan credentials land per-harness tiers
  (CLAUDE_CODE_OAUTH_TOKEN registers in the agent tier), resolve from
  the secrets manifest instead of assuming env.tier-llm

💘 Generated with Crush

---------

Co-authored-by: Agent Zero <agent.zero@pmoves.ai>

…dy ACK (#2998)

* docs(register): five-PR merge wave closeout — RELEASE rows + three-body ACK

RELEASE rows for archon-native (#2943), pair-review (#2946),
a0-archon-bridge (#2942), gh-app mint (#2959), H3 V3 archive (#2980).
Signoff checklist carries the wave's delivery/control/memory ACKs;
control is the operator's in-session merge directive. Learnings artifacts
stayed runtime-generated per protocol.

💘 Generated with Crush

* fix(register): declare CRUSH-SPARK (KIMI) and the kimi-k2 model token

The 2026-09-08 RELEASE rows signed as CRUSH-SPARK (KIMI) -- the model+node
decoration shape the vocabulary already documents for CRUSH-GLM52 (Z890).
Alias folded to the crush identity; KIMI declared as the kimi-k2 model.

💘 Generated with Crush

---------

Co-authored-by: Agent Zero <agent.zero@pmoves.ai>